[Top] [Prev] [Next] [Bottom] [Contents]

The Future

Sapphire 4.0 will also provide a choice of delivering the server applications in Java as well as C/C++. A Sapphire Java client application will thus be a pure Java solution with both parts running everywhere. Most Sapphire 3.0 applications will be able to upgrade to Java server deployment with no code or logic changes. Just change a project option and deploy. Two examples are the demo applications javaclient and activexclient. Some Sapphire/Web 3.0 applications may need some simple changes for the upgrade. C/C++ deployment will be still available since it offers better performance and scaleability.

A Sapphire/Web 4.0 server-side Java solution will incorporate the following enterprise technologies:

JDBC
RMI
IIOP
ADO Java classes
Jeeves with servlet technology
Other database connectivity options.

Delivery Sequence

Why did we deliver client-side Java first and server-side Java next? For several reasons.

: 1. Portability in the client is a requirement and Java offers that.
: 2. Java client technology is mature. The server side still lacked the enterprise APIs and was considered still immature at the time of V3.0 development.
: 3. The power of Java is in the client. A server-side approach where the power of Java was reduced to a simple print out of HTML tags will not port to the client.

The path we chose offers an upgrade to a pure Java solution with no code changes.

[Top] [Prev] [Next] [Bottom] [Contents]

info@bluestone.com

Copyright © 1997, Bluestone. All rights reserved.